Spatial data collection

ABSTRACT

A system and method for spatial data collection are described. Sensor data related to a position and an orientation of a device are generated over time using sensors of the device. Augmented reality content is generated based on a physical object captured by the device. A path bundle data package identifying a user interaction of the device with the augmented reality content relative to the physical object is generated. The user interaction identifies a spatial path of an interaction with the augmented reality content. The path bundle data package is generated based on the sensor data using a data model comprising a data header and a data payload. The data header comprises a contextual header having data identifying the device and a user of the device. A path header includes data identifying the path of the interaction with the augmented reality content. A sensor header includes data identifying the sensors. The data payload comprises dynamically sized sampling data from the sensor data.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is related to U.S. patent application Ser. No. ______, filed Aug. ______, 2014, entitled “SPATIAL DATA PROCESSING,” and U.S. patent application Ser. No. ______, filed Aug. ______, 2014, entitled “SPATIAL DATA VISUALIZATION,” which are incorporated herein by reference in their entirety.

TECHNICAL FIELD

The subject matter disclosed herein generally relates to the processing of data. Specifically, the present disclosure addresses systems and methods for spatial data collection and organization for augmented reality, virtual reality, and other mixed reality.

BACKGROUND

A device can be used to generate and display data in addition to an image captured with the device. For example, augmented reality (AR) is a live, direct or indirect view of a physical, real-world environment whose elements are augmented by computer-generated sensory input such as sound, video, graphics or GPS data. With the help of advanced AR technology (e.g., adding computer vision and object recognition) the information about the surrounding real world of the user becomes interactive. Device-generated (e.g., artificial) information about the environment and its objects can be overlaid on the real world.

BRIEF DESCRIPTION OF THE DRAWINGS

Some embodiments are illustrated by way of example and not limitation in the figures of the accompanying drawings.

FIG. 1 is a block diagram illustrating an example of a network suitable for spatial data collection for augmented reality experiences, according to some example embodiments.

FIG. 2 is a block diagram illustrating an example embodiment of modules (e.g., components) of a viewing device.

FIG. 3 is a block diagram illustrating an example embodiment of modules of a data aggregation module.

FIG. 4 is a block diagram illustrating an example embodiment of modules of a server.

FIG. 5 is a diagram illustrating an example embodiment of a path bundle packaged data model.

FIG. 6 is a diagram illustrating an example of a path bundle packaged data model.

FIG. 7 is a diagram illustrating another example of a path bundle packaged data model.

FIG. 8 is a diagram illustrating an example of a path bundle streaming data model.

FIG. 9 is a ladder diagram illustrating an example embodiment of an operation of the spatial data collection.

FIG. 10 is a flowchart illustrating an example operation of spatial data collection.

FIG. 11 is a block diagram illustrating components of a machine, according to some example embodiments, able to read instructions from a machine-readable medium and perform any one or more of the methodologies discussed herein.

FIG. 12 is a block diagram illustrating a mobile device, according to an example embodiment.

DETAILED DESCRIPTION

Example methods and systems are directed to spatial and sensor data collection of augmented reality. Examples merely typify possible variations. Unless explicitly stated otherwise, components and functions are optional and may be combined or subdivided, and operations may vary in sequence or be combined or subdivided. In the following description, for purposes of explanation, numerous specific details are set forth to provide a thorough understanding of example embodiments. It will be evident to one skilled in the art, however, that the present subject matter may be practiced without these specific details.

Augmented reality applications allow a user to experience information, such as in the form of a virtual object such as a three-dimensional virtual object overlaid on an image of a physical object captured with a camera of a viewing device. The physical object may include a visual reference (e.g., a recognized image, pattern, or object) that the augmented reality application can identify. A visualization of the additional information, such as the three-dimensional virtual object overlaid or engaged with an image of the physical object, is generated in a display of the viewing device. The three-dimensional virtual object may be selected based on the recognized visual reference or captured image of the physical object. A rendering of the visualization of the three-dimensional virtual object may be based on a position of the display relative to the visual reference. Other augmented reality applications allow a user to experience visualization of the additional information overlaid on top of a view or an image of any object in the real physical world. The virtual object may include a three-dimensional virtual object and/or a two-dimensional virtual object. For example, the three-dimensional virtual object may include a three-dimensional view of a chair or an animated dinosaur. The two-dimensional virtual object may include a two-dimensional view of a dialog box, menu, or written information such as statistics information for properties or physical characteristics of the object (e.g., temperature, mass, velocity, tension, stress). An image of the virtual object may be rendered at the viewing device or at a server in communication with the viewing device.

A system and method for spatial data collection are described. In one example embodiment, sensor data related to a position and an orientation of a viewing device are generated over time using sensors of the viewing device. Augmented reality content is generated based on a physical object captured by the viewing device. A path bundle data package identifying a user interaction of the viewing device with the augmented reality content relative to the physical object is generated. The user interaction identifies a spatial path of an interaction with the augmented reality content. The path bundle data package is generated based on the sensor data using a data model comprising a data header and a data payload. The data header comprises a contextual header having data identifying the viewing device and a user of the viewing device. A path header includes data identifying the sensor data and spatial information of the interaction with the augmented reality content. A sensor header includes data identifying and describing the sensors and any needed calibration or initialization data. The data payload comprises dynamically sized sampling data from the sensor data. The sensors may include any number of arbitrary sensors, including but not limited to optical sensors and inertial sensors. The viewing device may include a display configured to display the augmented reality content.

In one example embodiment, the augmented reality content comprises a virtual object generated based on the physical object identified and/or tracked with at least one of the sensors of the viewing device. The virtual object may include a three-dimensional model. A view of the three-dimensional model is dynamically adjusted based on the position and orientation of the viewing device relative to the physical object.

In one example embodiment, the contextual header comprises a viewing device identifier, a session identifier, a physical location, and a viewing device type. The path header comprises a path start time, a path end time, a type of sensor identifier for each corresponding sensor, a total duration of the path, a total distance of the path. The sensor header comprises, for each sensor, a sensor identifier, a sensor position identifier, three dimensional position data, orientation data, and a number of data samples. The dynamically sized sampling data comprises a sensor identifier, a data sample number, a relative time, a duration percentage through the path, and a time percentage through the path.

In one example embodiment, a data aggregation module of the viewing device aggregates sensor data from the plurality of sensors using the data model. The path of the interaction includes a spatial path relative to the augmented reality content. The data aggregation module generates a path bundle streaming data package. The path bundle streaming data package comprises the path bundle data package without data points that require information generated after the data point is generated.

In one example embodiment, a transparent display of a head-mounted wearable device displays the augmented reality content. A position and size of the augmented reality content in the transparent display are based on a position and orientation of the viewing device relative to the physical object.

In another example embodiment, a non-transitory machine-readable storage device may store a set of instructions that, when executed by at least one processor, cause the at least one processor to perform the method operations discussed within the present disclosure.

FIG. 1 is a network diagram illustrating a network environment 100 suitable for operating an augmented reality application of a viewing device, according to some example embodiments. The network environment 100 includes a viewing device 101 and a server 110, communicatively coupled to each other via a network 108. The viewing device 101 and the server 110 may each be implemented in a computer system, in whole or in part, as described below with respect to FIGS. 11 and 12.

The server 110 may be part of a network-based system. For example, the network-based system may be or include a cloud-based server system that provides additional information, such as three-dimensional models or other virtual objects, to the viewing device 101.

A user 102 may utilize the viewing device 101 to track a physical object 116 in a real world physical environment 114 viewed by the user 102. The user 102 may be a human user (e.g., a human being), a machine user (e.g., a computer configured by a software program to interact with the viewing device 101), or any suitable combination thereof (e.g., a human assisted by a machine or a machine supervised by a human). The user 102 is not part of the network environment 100, but is associated with the viewing device 101 and may be a user 102 of the viewing device 101. For example, the viewing device 101 may be a computing device with a display such as a smartphone, a tablet computer, a wearable computing device (e.g., watch or glasses), or a head-mounted computing device (e.g. helmet). The computing device may be hand held or may be removably mounted to the head of the user 102. In one example, the display may be a screen that displays what is captured with a camera of the viewing device 101. In another example, the display of the viewing device 101 may be transparent or semi-transparent such as in lenses of wearable computing glasses or the visor of a helmet. The viewing device 101 may include optical and non-optical sensors for identifying the physical object 116 and the position and orientation of the viewing device 101 relative to the physical object 116.

The user 102 may be a user of an augmented reality application in the viewing device 101 and at the server 110. The augmented reality application may provide the user 102 with an augmented experience triggered by identified objects or references in the physical environment 114. The physical environment 114 may include identifiable objects such as a two-dimensional physical object (e.g., a picture), a three-dimensional physical object (e.g., a factory machine), a location (e.g., at the bottom floor of a factory), or any references (e.g., perceived corners of walls or furniture) in the real world physical environment 114. For example, the user 102 may point a camera of the viewing device 101 to capture an image of the physical object 116.

In one embodiment, the objects in the image are tracked and recognized locally in the viewing device 101 using a local context recognition dataset or any other previously stored dataset of the augmented reality application of the viewing device 101. The local context recognition dataset module may include a library of virtual objects associated with real-world physical objects 116 or references. In one example, the viewing device 101 identifies feature points in an image of the physical object 116 to determine different planes (e.g., edges, corners, surface). The viewing device 101 also identifies tracking data related to the physical object 116 (e.g., GPS location of a bridge, facing west, e.g., viewing device 101 standing x meters away from the bridge, etc.). If the captured image is not recognized locally at the viewing device 101, the viewing device 101 downloads additional information (e.g., the three-dimensional model) corresponding to the captured image, from a database of the server 110 over the network 108.

In another embodiment, the image of the physical object 116 is tracked and recognized remotely at the server 110 using a remote context recognition dataset or any other previously stored dataset of an augmented reality application in the server 110. The remote context recognition dataset module may include a library of virtual objects associated with real-world physical objects 116 or references.

Sensors 112 may be associated with, coupled to, related to the physical object 116 in the physical environment 114 to measure properties of the physical object 116. Examples of measured physical properties may include but are not limited to weight, pressure, temperature, velocity, direction, position, intrinsic and extrinsic properties, acceleration, and dimensions. For example, the sensors 112 may include a blood pressure and heart rate monitor coupled to a subject. For example, the server 110 can generate a picture or a virtual three-dimensional model of a heart with a beating animation with a pace corresponding to the measured heart rate from the sensors 112. The server 110 may change a color in corresponding portions of the heart based on the measured blood pressure. The live animation is provided to the viewing device 101 such that the picture of the heart is displayed on top of a chest area of the subject in the display of the viewing device 101. The position of the picture of the heart may be determined based on the orientation and position of the viewing device 101 relative to the subject using sensors (e.g., gyroscope) internal to the viewing device 101.

In another embodiment, the sensors 112 may include other sensors used to track the location, movement, and orientation of the viewing device 101 externally without having to rely on the sensors internal to the viewing device 101. The sensors 112 may include optical sensors (e.g., depth-enabled 3D camera), wireless sensors (Bluetooth, Wi-Fi), GPS sensor, and audio sensor to determine the location of the user 102 having the viewing device 101, distance of the user 102 to the tracking sensors 112 in the physical environment 114 (e.g., sensors 112 placed in corners of a venue or a room), the orientation of the viewing device 101 to track what the user 102 is looking at (e.g., direction at which the viewing device 101 is pointed, viewing device 101 pointed towards a player on a tennis court, viewing device 101 pointed at a person in a room).

In another embodiment, data from the sensors 112 and internal sensors in the viewing device 101 may be used for analytics data processing at the server 110 (or another server) for analysis on usage and how the user 102 is interacting with the physical environment 114 and the virtual content based on the physical object 116. Live data from other servers 110 may also be used in the analytics data processing. For example, the analytics data may track at what locations (e.g., points or features) on the physical or virtual object the user 102 has looked, how long the user 102 has looked at each location on the physical or virtual object, how the user 102 held the viewing device 101 when looking at the physical or virtual object, which features of the virtual object the user 102 interacted with (e.g., such as whether a user 102 tapped on a link in the virtual object), and any suitable combination thereof. The viewing device 101 receives a visualization content dataset related to the analytics data. The viewing device 101 then generates a virtual object with additional or visualization features, or a new experience, based on the visualization content dataset.

Any of the machines, databases, or devices shown in FIG. 1 may be implemented in a general-purpose computer modified (e.g., configured or programmed) by software to be a special-purpose computer to perform one or more of the functions described herein for that machine, database, or device. For example, a computer system able to implement any one or more of the methodologies described herein is discussed below with respect to FIGS. 11, 12. As used herein, a “database” is a data storage resource and may store data structured as a text file, a table, a spreadsheet, a relational database (e.g., an object-relational database), a triple store, a hierarchical data store, or any suitable combination thereof. Moreover, any two or more of the machines, databases, or devices illustrated in FIG. 1 may be combined into a single machine, and the functions described herein for any single machine, database, or device may be subdivided among multiple machines, databases, or devices.

The network 108 may be any network that enables communication between or among machines (e.g., server 110), databases, and devices (e.g., device 101). Accordingly, the network 108 may be a wired network, a wireless network (e.g., a mobile or cellular network), or any suitable combination thereof. The network 108 may include one or more portions that constitute a private network, a public network (e.g., the Internet), or any suitable combination thereof.

FIG. 2 is a block diagram illustrating modules (e.g., components) of the viewing device 101, according to some example embodiments. The viewing device 101 may include sensors 202, a display 204, a processor 206, and a storage device 208. For example, the viewing device 101 may be a wearing computing device (e.g., glasses or helmet), a desktop computer, a vehicle computer, a tablet computer, a navigational device, a portable media device, or a smart phone of a user 102. The user 102 may be a human user (e.g., a human being), a machine user (e.g., a computer configured by a software program to interact with the viewing device 101), or any suitable combination thereof (e.g., a human assisted by a machine or a machine supervised by a human).

The sensors 202 may include, for example, a proximity or location sensor (e.g., near field communication, GPS, Bluetooth, Wi-Fi), an optical sensor (e.g., infrared camera, time of flight sensors, structured light sensors), inertial sensors, compass, gyroscope, temperature sensors, humidity sensors, an audio sensor (e.g., a microphone), or any suitable combination thereof. For example, the sensors 202 may include a rear facing camera and a front facing camera in the viewing device 101. It is noted that the sensors 202 described herein are for illustration purposes; the sensors 202 are thus not limited to the ones described. The sensors 202 may be used to generate internal tracking data of the viewing device 101 to determine what the viewing device 101 is capturing or looking at in the real physical world.

The display 204 may include, for example, a touchscreen display configured to receive a user input via a contact on the touchscreen display. In one example, the display 204 may include a screen or monitor configured to display images generated by the processor 206. In another example, the display 204 may be transparent or semi-opaque so that the user 102 can see through the display 204 (e.g., head-up display, see through screen).

The processor 206 may include an augmented reality application 216 for generating a display of a three-dimensional virtual object related to a physical object 116 captured by the viewing device 101. In one example embodiment, the augmented reality application 216 may include an augmented reality processing module 214 and a data aggregation module 218.

The augmented reality processing module 214 identifies a physical object 116 that the viewing device 101 is pointed to. The augmented reality processing module 214 may detect, generate, and identify identifiers such as feature points of the physical object 116 being viewed or pointed at the viewing device 101 using an optical device of the viewing device 101 to capture the image of the physical object 116. As such, the augmented reality processing module 214 may be configured to identify one or more physical objects 116. The identification of the object may be performed in many different ways. For example, feature points of the physical object 116 may be determined based on several image frames of the physical object 116. The identity of the physical object 116 may be also determined using any visual recognition algorithm. In another example, a unique identifier may be associated with the physical object 116. The unique identifier may be a unique wireless signal or a unique visual pattern such that the augmented reality processing module 214 can look up the identity of the physical object 116 based on the unique identifier from a local or remote content database. In another example embodiment, the augmented reality processing module 214 includes a facial recognition algorithm to determine an identity of a subject or object. The augmented reality processing module 214 may be configured to determine whether the captured image matches an image locally stored in a local database of images and corresponding additional information (e.g., three-dimensional model and interactive features) on the viewing device 101. In one embodiment, the augmented reality processing module 214 retrieves a primary content dataset from the server 110, and generates and updates a contextual content dataset based an image captured with the viewing device 101.

The augmented reality processing module 214 may include a local rendering engine that generates a visualization of a three-dimensional virtual object overlaid (e.g., superimposed upon, or otherwise displayed in tandem with) on an image of a physical object 116 captured by a camera of the viewing device 101 in the display 204 of the viewing device 101. A visualization of the three-dimensional virtual object may be manipulated by adjusting a position of the physical object 116 (e.g., its physical location, orientation, or both) relative to the camera of the viewing device 101. Similarly, the visualization of the three-dimensional virtual object may be manipulated by adjusting a position of the camera of the viewing device 101 relative to the physical object 116.

In another example embodiment, the augmented reality processing module 214 may retrieve three-dimensional models of virtual objects associated with a captured real world object. For example, the captured image may include a visual reference (also referred to as a marker) that consists of an identifiable image, symbol, letter, number, machine-readable code. For example, the visual reference may include a bar code, a quick response (QR) code, or an image that has been previously associated with a three-dimensional virtual object (e.g., an image that has been previously determined to correspond to the three-dimensional virtual object).

The data aggregation module 218 may be configured to access data from the sensors 202 and aggregate the data using a path bundle packaged data model. The data aggregation module 218 collects spatial positioning, movement and sensor data attached to an augmented reality event flow. This process includes the data organization format and process for linking the positioning, movement and sensor data to other non-spatial/sensor data. In an example embodiment, the path bundle packaged data model includes separating the data into a header that contains contextual and technical/calibration information, and the payload, which contains the actual spatial and sensor data. The header information is organized to contain information specific to the path context, like the AR session linked to the path, the time, the location (which may be moved to the payload), the device type, the user 102, etc. The header also includes technical/calibration information specific to the path data itself, such as a listing all of the sensors 202 being captured, specific data about their frequency/thresholds, an initial camera matrix, start time/end time, etc. The payload contains the spatial/sensor data encapsulated in such a way that multiple data points can be tied together when processing (typically via time, but also possibly through other means like step number, or percentage of path). The creation of this data model allows the capture of spatial and analytics data across multiple devices and combine, aggregate and/or filter it without modifying the original pure data stream.

In an example embodiment depicted in FIG. 2, the data aggregation module 218 includes a contextual data module 302, a path data module 304, a sensor data module 306, and a bundle module 308. The contextual data module 302 generates data related to the user 102 and the viewing device 101 attached to the path. Contextual data may change from path to path but may not be directly related to data samples collected. The path data module 304 generates data related to the corresponding path bundle. That data may change for each data sample, but may not change for all the sample points within the path. The data from the path data module 304 may also list a number and type of sensors 202 collected. The sensor data module 306 generates data related to each specific sensor 202 for a path. For example, the data from the sensor data module 306 may include technical information about their collection such as the sample frequency or the threshold that will trigger a non-frequency-based sample. The bundle module 308 aggregates data from the contextual data module 302, path data module 304, the sensor data module 306, and sampling data from the sensors 202 using a path bundle packaged data model. The sampling data includes, for example, dynamically sized series of data samples that indicate which sensor 202 is used, the sensor-specific data, the time of the sample, the step number of the sample, whether it was frequency or threshold triggered, etc.

The storage device 208 may be configured to store the path bundle packaged data, a database of identifiers of physical objects 116, tracking data, and corresponding virtual user interfaces. In another embodiment, the database may also include visual references (e.g., images) and corresponding experiences (e.g., three-dimensional virtual objects, interactive features of the three-dimensional virtual objects). For example, the visual reference may include a machine-readable code or a previously identified image (e.g., a picture of a shoe). The previously identified image of the shoe may correspond to a three-dimensional virtual model of the shoe that can be viewed from different angles by manipulating the position of the viewing device 101 relative to the picture of the shoe. Features of the three-dimensional virtual shoe may include selectable icons on the three-dimensional virtual model of the shoe. An icon may be selected or activated by tapping on or moving the viewing device 101.

In one embodiment, the storage device 208 includes a primary content dataset, a contextual content dataset, and a visualization content dataset. The primary content dataset includes, for example, a first set of images and corresponding experiences (e.g., interaction with three-dimensional virtual object models). For example, an image may be associated with one or more virtual object models. The primary content dataset may include a core set of images or the most popular images determined by the server 110. The core set of images may include a limited number of images identified by the server 110. For example, the core set of images may include the images depicting covers of the ten most popular magazines and their corresponding experiences (e.g., virtual objects that represent the ten most popular magazines). In another example, the server 110 may generate the first set of images based on the most popular or often scanned images received at the server 110. Thus, the primary content dataset does not depend on objects or images scanned by AR processing module 214.

The contextual content dataset includes, for example, a second set of images and corresponding experiences (e.g., three-dimensional virtual object models) retrieved from the server 110. For example, images captured with the viewing device 101 that are not recognized (e.g., by the server 110) in the primary content dataset are submitted to the server 110 for recognition. If the captured image is recognized by the server 110, a corresponding experience may be downloaded at the viewing device 101 and stored in the contextual content dataset. Thus, the contextual content dataset relies on the context in which the viewing device 101 has been used. As such, the contextual content dataset depends on objects or images scanned by the AU processing module 214 of the viewing device 101.

In one embodiment, the viewing device 101 may communicate over the network 108 with the server 110 to retrieve a portion of a database of visual references, corresponding three-dimensional virtual objects, and corresponding interactive features of the three-dimensional virtual objects.

Any one or more of the modules described herein may be implemented using hardware (e.g., a processor 206 of a machine) or a combination of hardware and software. For example, any module described herein may configure a processor 206 to perform the operations described herein for that module. Moreover, any two or more of these modules may be combined into a single module, and the functions described herein for a single module may be subdivided among multiple modules. Furthermore, according to various example embodiments, modules described herein as being implemented within a single machine, database, or device may be distributed across multiple machines, databases, or devices.

FIG. 4 is a block diagram illustrating modules (e.g., components) of the server 110. The server 110 includes a processor 402 and a database 410. The processor 402 may include a path bundle processing module 404, a visualization module 406. The path bundle processing module 404 performs aggregation, filtering and any non-visual processing (pattern recognition, predictive analysis) on the raw data paths. The visualization module 406 uses algorithms to combine the processed path bundles with the original models/assets to generate visually processed data and convert it to a report, visual display or AR experience.

The database 410 may store a content dataset 412, a virtual content dataset 414, and path bundle dataset 416. The content dataset 412 may store a primary content dataset and a contextual content dataset. The primary content dataset comprises a first set of images and corresponding virtual object models. A captured image received from the viewing device 101 is not recognized in the content dataset 412, and the contextual content dataset is generated for the viewing device 101. The contextual content dataset may include a second set of images and corresponding virtual object models. The virtual content dataset 414 includes models of virtual objects to be generated upon receiving a notification associated with an image of a corresponding physical object 116. The path bundle dataset 416 includes visually processed data and/or raw data paths.

FIG. 5 is a diagram illustrating an example embodiment of a path bundle packaged data model 500. The data model may include a data header 502, and a data payload 504. The data header 502 may include a contextual header 506, a path header 508, and a sensor header 510. The data payload 504 may include sampling data 512. The contextual header 506 may include, for example, data related to a user 102 and a viewing device 101 attached to the path. The data may change from path to path and may not be directly related to the data samples collected. The path header 508 includes data related to the corresponding path bundle. That data may change from each instead of a new path, but may not change for all the sample points within the path. The data from the path header 508 may also list a number and type of sensors 202 collected. The sensor header 510 includes data related to each specific sensor 202 for a path and includes technical information about their collection such as the sample frequency or the threshold that triggers a non-frequency-based sample. The sampling data 512 includes, for example, dynamically sized series of data samples that indicate which sensor 202 is used, the time of the sample, the step number of the sample, whether it was frequency or threshold triggered, etc.

FIG. 6 is a diagram illustrating an example of a path bundle packaged data model 500. The contextual header 602 includes, for example, a device identifier, a session identifier, location information, and a device type. The path header 604 includes, for example, a path start time, a name and type of sensors, a total path duration, and a total path distance. The sensor header 606 includes, for each sensor, for example, sensor 1, a sensor name, a type of sensor, an initial calibration, a frequency, a threshold, and a number of samples. The sampling data 608 includes, for each sensor sample, a sample number, a frequency, a relative time, a duration percentage of the path, a time percentage of the path.

FIG. 7 is a diagram illustrating another example of a path bundle packaged data model 500. The path bundle packaged data model 500 includes a contextual header example 702, a path header example 704, a sensor header example 706, a sampling data example 708.

The contextual header 702 may include, for example:

Device ID: ABCDE12345 Session ID: 23 Location: Los Angeles, Calif., US Device Type: Tablet

The path header 704 may include, for example:

Path Start: 2014-02-21T16:03:22.50 Sensor 1—Camera, Sensor 2—Camera, Sensor 3—Temperature Total Duration: 60 s Total Path—25 cm

The sensor header 606 may include, for example:

Sensor 1 Left Eye Camera

[0.2,0.1,0.1] 5 s 5 deg 12 samples

The sampling data 608 may include, for example:

Left Eye Sample 1 (F)

16:05:15 8% through Time 20% through Path

X,Y,Z

The path bundle packaged data model 500 may be linked to an event flow 710 by session identifier and time. For example, the event flow 710 may include when a particular session started 710, a starting time 712, a requested information and corresponding time 714, a hazard identification and corresponding time 716, a remediation identification and a corresponding time 718, a process completion identification and a corresponding time 720, and an end time for the session 722. The hazard identification may be based on the sensor data. For example, the thermal sensor may show that the temperature has exceeded a predefined threshold that is deemed dangerous for the user 102.

FIG. 8 is a diagram illustrating another example of a path bundle streaming data model. The path bundle packaged data model 500 includes a contextual header example 802, a path header example 804, a sensor header example 806, and a sampling data example 808.

FIG. 9 is a ladder diagram illustrating an example embodiment of an operation of the spatial data collection. At operation 902, the viewing device 101 generates augmented reality content based on a physical object 116. At operation 904, the viewing device 101 accesses sensor data from the viewing device 101. At operation 906, the viewing device 101 aggregates sensor data using a data model to generate raw path bundles. At operation 908, the viewing device 101 communicates the raw path bundles to the server 110 for storage and processing. The server 110 stores raw path bundles at operation 910. The server 110 processes the raw path bundles at operation 912. The server 110 generates a visualization based on the processed raw path bundles at operation 914.

FIG. 10 is a flowchart illustrating an example operation of spatial data collection. At operation 1002, the viewing device 101 accesses sensor data. At operation 1004, the viewing device 101 generates augmented reality content. At operation 1006, the viewing device 101 generates raw path bundles from the sensor data using a data model. At operation 1008, the viewing device 101 sends the raw path bundles data using the data model to the server 110 for processing.

Modules, Components and Logic

Certain embodiments are described herein as including logic or a number of components, modules, or mechanisms. Modules may constitute either software modules (e.g., code embodied on a machine-readable medium or in a transmission signal) or hardware modules. A hardware module is a tangible unit capable of performing certain operations and may be configured or arranged in a certain manner. In example embodiments, one or more computer systems (e.g., a standalone, client, or server computer system) or one or more hardware modules of a computer system (e.g., a processor or a group of processors 402) may be configured by software (e.g., an application or application portion) as a hardware module that operates to perform certain operations as described herein.

In various embodiments, a hardware module may be implemented mechanically or electronically. For example, a hardware module may comprise dedicated circuitry or logic that is permanently configured (e.g., as a special-purpose processor, such as a field programmable gate array (FPGA) or an application-specific integrated circuit (ASIC)) to perform certain operations. A hardware module may also comprise programmable logic or circuitry (e.g., as encompassed within a general-purpose processor or other programmable processor 402) that is temporarily configured by software to perform certain operations. It will be appreciated that the decision to implement a hardware module mechanically, in dedicated and permanently configured circuitry, or in temporarily configured circuitry (e.g., configured by software) may be driven by cost and time considerations.

Accordingly, the term “hardware module” should be understood to encompass a tangible entity, be that an entity that is physically constructed, permanently configured (e.g., hardwired) or temporarily configured (e.g., programmed) to operate in a certain manner and/or to perform certain operations described herein. Considering embodiments in which hardware modules are temporarily configured (e.g., programmed), each of the hardware modules need not be configured or instantiated at any one instance in time. For example, where the hardware modules comprise a general-purpose processor 402 configured using software, the general-purpose processor 402 may be configured as respective different hardware modules at different times. Software may accordingly configure a processor 402, for example, to constitute a particular hardware module at one instance of time and to constitute a different hardware module at a different instance of time.

Hardware modules can provide information to, and receive information from, other hardware modules. Accordingly, the described hardware modules may be regarded as being communicatively coupled. Where multiple of such hardware modules exist contemporaneously, communications may be achieved through signal transmission (e.g., over appropriate circuits and buses) that connect the hardware modules. In embodiments in which multiple hardware modules are configured or instantiated at different times, communications between such hardware modules may be achieved, for example, through the storage and retrieval of information in memory structures to which the multiple hardware modules have access. For example, one hardware module may perform an operation and store the output of that operation in a memory device to which it is communicatively coupled. A further hardware module may then, at a later time, access the memory device to retrieve and process the stored output. Hardware modules may also initiate communications with input or output devices and can operate on a resource (e.g., a collection of information).

The various operations of example methods described herein may be performed, at least partially, by one or more processors 402 that are temporarily configured (e.g., by software) or permanently configured to perform the relevant operations. Whether temporarily or permanently configured, such processors 402 may constitute processor-implemented modules that operate to perform one or more operations or functions. The modules referred to herein may, in some example embodiments, comprise processor-implemented modules.

Similarly, the methods described herein may be at least partially processor-implemented. For example, at least some of the operations of a method may be performed by one or more processors 402 or processor-implemented modules. The performance of certain of the operations may be distributed among the one or more processors 402, not only residing within a single machine, but deployed across a number of machines. In some example embodiments, the processor or processors 402 may be located in a single location (e.g., within a home environment, an office environment or as a server farm), while in other embodiments the processors 402 may be distributed across a number of locations.

The one or more processors 402 may also operate to support performance of the relevant operations in a “cloud computing” environment or as a “software as a service” (SaaS). For example, at least some of the operations may be performed by a group of computers (as examples of machines including processors 402), these operations being accessible via a network and via one or more appropriate interfaces (e.g., APIs).

Electronic Apparatus and System

Example embodiments may be implemented in digital electronic circuitry, or in computer hardware, firmware, software, or in combinations of them. Example embodiments may be implemented using a computer program product, e.g., a computer program tangibly embodied in an information carrier, e.g., in a machine-readable medium for execution by, or to control the operation of, data processing apparatus, e.g., a programmable processor 402, a computer, or multiple computers.

A computer program can be written in any form of programming language, including compiled or interpreted languages, and it can be deployed in any form, including as a stand-alone program or as a module, subroutine, or other unit suitable for use in a computing environment. A computer program can be deployed to be executed on one computer or on multiple computers at one site or distributed across multiple sites and interconnected by a communication network 108.

In example embodiments, operations may be performed by one or more programmable processors 402 executing a computer program to perform functions by operating on input data and generating output. Method operations can also be performed by, and apparatus of example embodiments may be implemented as, special purpose logic circuitry (e.g., a FPGA or an ASIC).

A computing system can include clients and servers 110. A client and server 110 are generally remote from each other and typically interact through a communication network 108. The relationship of client and server 110 arises by virtue of computer programs running on the respective computers and having a client-server relationship to each other. In embodiments deploying a programmable computing system, it will be appreciated that both hardware and software architectures merit consideration. Specifically, it will be appreciated that the choice of whether to implement certain functionality in permanently configured hardware (e.g., an ASIC), in temporarily configured hardware (e.g., a combination of software and a programmable processor), or a combination of permanently and temporarily configured hardware may be a design choice. Below are set out hardware (e.g., machine) and software architectures that may be deployed, in various example embodiments.

Example Machine Architecture and Machine-Readable Medium

FIG. 11 is a block diagram of a machine in the example form of a computer system 1100 within which instructions 1124 for causing the machine to perform any one or more of the methodologies discussed herein may be executed. In alternative embodiments, the machine operates as a standalone device or may be connected (e.g., networked) to other machines. In a networked deployment, the machine may operate in the capacity of a server 110 or a client machine in a server-client network environment 100, or as a peer machine in a peer-to-peer (or distributed) network environment 100. The machine may be a personal computer (PC), a tablet PC, a set-top box (STB), a personal digital assistant (PDA), a cellular telephone, a web appliance, a network router, switch or bridge, or any machine capable of executing instructions 1124 (sequential or otherwise) that specify actions to be taken by that machine. Further, while only a single machine is illustrated, the term “machine” shall also be taken to include any collection of machines that individually or jointly execute a set (or multiple sets) of instructions 1124 to perform any one or more of the methodologies discussed herein.

The example computer system 1100 includes a processor 1102 (e.g., a central processing unit (CPU), a graphics processing unit (GPU) or both), a main memory 1104 and a static memory 1106, which communicate with each other via a bus 1108. The computer system 1100 may further include a video display unit 1110 (e.g., a liquid crystal display (LCD) or a cathode ray tube (CRT)). The computer system 1100 also includes an alphanumeric input device 1112 (e.g., a keyboard), a user interface (UI) navigation (or cursor control) device 1114 (e.g., a mouse), a disk drive unit 1116, a signal generation device 1118 (e.g., a speaker) and a network interface device 1120.

Machine-Readable Medium

The disk drive unit 1116 includes a machine-readable medium 1122 on which is stored one or more sets of data structures and instructions 1124 (e.g., software) embodying or utilized by any one or more of the methodologies or functions described herein. The instructions 1124 may also reside, completely or at least partially, within the main memory 1104 and/or within the processor 1102 during execution thereof by the computer system 1100, the main memory 1104 and the processor 1102 also constituting machine-readable media 1122. The instructions 1124 may also reside, completely or at least partially, within the static memory 1106 (not shown).

While the machine-readable medium 1122 is shown in an example embodiment to be a single medium, the term “machine-readable medium” may include a single medium or multiple media (e.g., a centralized or distributed database 410, and/or associated caches and servers) that store the one or more instructions 1124 or data structures. The term “machine-readable medium” shall also be taken to include any tangible medium that is capable of storing, encoding or carrying instructions 1124 for execution by the machine and that cause the machine to perform any one or more of the methodologies of the present embodiments, or that is capable of storing, encoding or carrying data structures utilized by or associated with such instructions 1124. The term “machine-readable medium” shall accordingly be taken to include, but not be limited to, solid-state memories, and optical and magnetic media. Specific examples of machine-readable media 1122 include non-volatile memory including, by way of example, semiconductor memory devices (e.g., erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), and flash memory devices); magnetic disks such as internal hard disks and removable disks; magneto-optical disks; and compact disc-read-only memory (CD-ROM) and digital versatile disc (or digital video disc) read-only memory (DVD-ROM) disks.

Transmission Medium

The instructions 1124 may further be transmitted or received over a communications network 1126 using a transmission medium. The instructions 1124 may be transmitted using the network interface device 1120 and any one of a number of well-known transfer protocols (e.g., HTTP). Examples of communication networks include a LAN, a WAN, the Internet, mobile telephone networks, POTS networks, and wireless data networks (e.g., WiFi and WiMax networks). The term “transmission medium” shall be taken to include any intangible medium capable of storing, encoding, or carrying instructions 1124 for execution by the machine, and includes digital or analog communications signals or other intangible media to facilitate communication of such software.

Example Mobile Device

FIG. 12 is a block diagram illustrating a mobile device 1200, according to an example embodiment. The mobile device 1200 may include a processor 1202. The processor 1202 may be any of a variety of different types of commercially available processors 1202 suitable for mobile devices 1200 (for example, an XScale architecture microprocessor, a microprocessor without interlocked pipeline stages (MIPS) architecture processor, or another type of processor 1202). A memory 1204, such as a random access memory (RAM), a flash memory, or other type of memory, is typically accessible to the processor 1202. The memory 1204 may be adapted to store an operating system (OS) 1206, as well as application programs 1208, such as a mobile location enabled application that may provide Location Based Services to a user 102. The processor 1202 may be coupled, either directly or via appropriate intermediary hardware, to a display 1210 and to one or more input/output (I/O) devices 1212, such as a keypad, a touch panel sensor, a microphone, and the like. Similarly, in some embodiments, the processor 1202 may be coupled to a transceiver 1214 that interfaces with an antenna 1216. The transceiver 1214 may be configured to both transmit and receive cellular network signals, wireless data signals, or other types of signals via the antenna 1216, depending on the nature of the mobile device 1200. Further, in some configurations, a GPS receiver 1218 may also make use of the antenna 1216 to receive GPS signals.

Although an embodiment has been described with reference to specific example embodiments, it will be evident that various modifications and changes may be made to these embodiments without departing from the broader spirit and scope of the present disclosure. Accordingly, the specification and drawings are to be regarded in an illustrative rather than a restrictive sense. The accompanying drawings that form a part hereof, show by way of illustration, and not of limitation, specific embodiments in which the subject matter may be practiced. The embodiments illustrated are described in sufficient detail to enable those skilled in the art to practice the teachings disclosed herein. Other embodiments may be utilized and derived therefrom, such that structural and logical substitutions and changes may be made without departing from the scope of this disclosure. This Detailed Description, therefore, is not to be taken in a limiting sense, and the scope of various embodiments is defined only by the appended claims, along with the full range of equivalents to which such claims are entitled.

Such embodiments of the inventive subject matter may be referred to herein, individually and/or collectively, by the term “invention” merely for convenience and without intending to voluntarily limit the scope of this application to any single invention or inventive concept if more than one is in fact disclosed. Thus, although specific embodiments have been illustrated and described herein, it should be appreciated that any arrangement calculated to achieve the same purpose may be substituted for the specific embodiments shown. This disclosure is intended to cover any and all adaptations or variations of various embodiments. Combinations of the above embodiments, and other embodiments not specifically described herein, will be apparent to those of skill in the art upon reviewing the above description.

The Abstract of the Disclosure is provided to comply with 37 C.F.R. §1.72(b), requiring an abstract that will allow the reader to quickly ascertain the nature of the technical disclosure. It is submitted with the understanding that it will not be used to interpret or limit the scope or meaning of the claims. In addition, in the foregoing Detailed Description, it can be seen that various features are grouped together in a single embodiment for the purpose of streamlining the disclosure. This method of disclosure is not to be interpreted as reflecting an intention that the claimed embodiments require more features than are expressly recited in each claim. Rather, as the following claims reflect, inventive subject matter lies in less than all features of a single disclosed embodiment. Thus the following claims are hereby incorporated into the Detailed Description, with each claim standing on its own as a separate embodiment. 

What is claimed is:
 1. A device comprising: a plurality of sensors configured to generate sensor data related to a position and an orientation of the device; a hardware processor comprising an augmented reality application, the augmented reality application including: an augmented reality processing module configured to generate augmented reality content based on a physical object captured by the device; a data aggregation module configured to generate a path bundle data package describing user interaction of the device with the augmented reality content relative to the physical object, the user interaction identifying a spatial path of an interaction with the augmented reality content, the path bundle data package generated based on the sensor data using a data model comprising a data header and a data payload, and the data header comprising a contextual header having data identifying the device and a user of the device, a path header having data identifying the spatial path of the interaction with the augmented reality content, and a sensor header having data identifying the plurality of sensors, the data payload comprising dynamically sized sampling data from the sensor data.
 2. The device of claim 1, wherein the plurality of sensors comprises optical sensors and inertial sensors.
 3. The device of claim 1, further comprising a display configured to display the augmented reality content, wherein the augmented reality content comprises a virtual object generated based on the physical object captured with at least one of the sensors of the device, the virtual object comprising a three-dimensional model, a view of the three-dimensional model dynamically adjusted based on the position and orientation of the device relative to the physical object.
 4. The device of claim 1, wherein the contextual header comprises a device identifier, a session identifier, a physical location, and a device type.
 5. The device of claim 1, wherein the path header comprises a path start time, a path end time, a type of sensor identifier for each corresponding sensor, a total duration of the path, and a total distance of the path.
 6. The device of claim 1, wherein the sensor header comprises, for each sensor, a sensor identifier, a sensor position identifier, three dimensional position data, orientation data, and a number of data samples.
 7. The device of claim 1, wherein the dynamically sized sampling data comprises a sensor identifier, a data sample number, sensor data, a relative time, a duration percentage through the path, and a time percentage through the path.
 8. The device of claim 1, wherein the data aggregation module is configured to aggregate sensor data from the plurality of sensors using the data model.
 9. The device of claim 1, wherein the path of the interaction comprises a spatial path relative to the augmented reality content.
 10. The device of claim 1, further comprising: the data aggregation module configured to generate a path bundle streaming data package, the path bundle streaming data package comprising the path bundle data package without data points where information is generated after the data point is generated.
 11. A method comprising: generating sensor data related to a position and an orientation of a device over time using a plurality of sensors of the device; generating, using a processor of a machine, augmented reality content based on a physical object captured by the device; and generating a path bundle data package describing a user interaction of the device with the augmented reality content relative to the physical object, the user interaction identifying a spatial path of an interaction with the augmented reality content, the path bundle data package generated based on the sensor data using a data model comprising a data header and a data payload, and the data header comprising a contextual header having data identifying the device and a user of the device, a path header having data identifying the path of the interaction with the augmented reality content, and a sensor header having data identifying the plurality of sensors, the data payload comprising dynamically sized sampling data from the sensor data.
 12. The method of claim 11, wherein the plurality of sensors comprises optical sensors and inertial sensors.
 13. The method of claim 11, further comprising: displaying the augmented reality content, wherein the augmented reality content comprises a virtual object generated based on the physical object captured with at least one of the sensors of the device, the virtual object comprising a three-dimensional model, a view of the three-dimensional model dynamically adjusted based on the position and orientation of the device relative to the physical object.
 14. The method of claim 11, wherein the contextual header comprises a device identifier, a session identifier, a physical location, and a device type.
 15. The method of claim 11, wherein the path header comprises a path start time, a path end time, a type of sensor identifier for each corresponding sensor, a total duration of the path, a total distance of the path.
 16. The method of claim 11, wherein the sensor header comprises, for each sensor, a sensor identifier, a sensor position identifier, three dimensional position data, orientation data, and a number of data samples.
 17. The method of claim 11, wherein the dynamically sized sampling data comprises a sensor identifier, a data sample number, sensor data, a relative time, a duration percentage through the path, and a time percentage through the path.
 18. The method of claim 11, further comprising aggregating sensor data from the plurality of sensors using the data model, wherein the path of the interaction comprises a spatial path relative to the augmented reality content.
 19. The method of claim 11, further comprising: generating a path bundle streaming data package, the path bundle streaming data package comprising the path bundle data package without data points where information is generated after the data point is generated; and displaying, in a transparent display of a head-mounted wearable device, the augmented reality content, a position and size of the augmented reality content in the transparent display based on a position and orientation of the device relative to the physical object.
 20. A non-transitory machine-readable medium comprising instructions that, when executed by one or more processors of a machine, cause the machine to perform operations comprising: generating sensor data related to a position and an orientation of a device over time using a plurality of sensors of the device; generating augmented reality content based on a physical object captured by the device; generating a path bundle data package describing a user interaction of the device with the augmented reality content relative to the physical object, the user interaction identifying a spatial path of an interaction with the augmented reality content, the path bundle data package generated based on the sensor data using a data model comprising a data header and a data payload, the data header comprising a contextual header having data identifying the device and a user of the device, a path header having data identifying the path of the interaction with the augmented reality content, and a sensor header having data identifying the plurality of sensors, the data payload comprising dynamically sized sampling data from the sensor data. 